Blog Post: Azure Front Door end-to-end TLS with AKS App Routing #4825
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is for a new blog post to the AKS blog that demonstrates setting up an AKS cluster with App Routing to host an internal endpoint to an application, including the creation of a private link. The post then walks through the set up of Azure Front Door to consume that private linked endpoint.
In the post I also show some steps for generating a certificate via either App Service Certificates or via LetsEncrypt using CertBot. That section can easily be removed if it doesnt seem to be a good fit.
In this PR I am also including my addition to the 'Authors' list of the site.